The KEY keyword was reserved in all contexts, preventing its use as column or table names. This caused parse errors for common schemas where "key" is a natural identifier (e.g., key-value stores, API keys).

Changes

Grammar modifications (src/alasqlparser.jison):

• Added KEY as explicit Literal alternative to allow use as identifier
• Removed standalone KEY Literal variant from IndexKey rule (eliminates parser ambiguity when parsing column definitions)
• Fixed IndexKey to use ColsList for consistency with PrimaryKey/ForeignKey

Test coverage (test/test2203.js):

• 13 test cases validating KEY works as column/table name in SELECT, WHERE, JOIN, GROUP BY, ORDER BY
• Verifies PRIMARY KEY, FOREIGN KEY, UNIQUE KEY syntax unchanged

Example

-- Now works without escaping
CREATE TABLE cache (id INT, key VARCHAR(50), data TEXT);
SELECT * FROM cache WHERE key = 'user:123';

-- Standard SQL KEY constructs still work
CREATE TABLE users (id INT PRIMARY KEY, email VARCHAR(100));
CREATE TABLE items (id INT, FOREIGN KEY (user_id) REFERENCES users(id));

Breaking Change

Index creation via KEY idx_name (column) no longer supported. Use INDEX idx_name (column) instead. This MySQL-specific variant was redundant with the standard INDEX keyword.

• Fixes Limit the impact of using the keyword: KEY #2227

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.